(External Link)

Scope

• Language
  • Computer-encoded text
    • Alphabets/scripts; different systems of numerals; left-to-right vs. right-to-left script. Most recent systems use the Unicode standard to solve many of these character encoding problems.
    • Spelling variants for different countries where the same language is spoken, for example localization (en-US, en-CA, en-GB-oed) vs. localisation (en-GB, en-AU)
  • Graphical representations of text (printed materials, online images containing text)
  • Spoken (Audio)
  • Subtitling of film and video
• Culture
  • Images and colors: issues of comprehensibility and cultural appropriateness
  • Names and titles
  • Government assigned numbers (such as the Social Security number in the US, National Insurance number in the UK) and passports
  • Telephone numbers, addresses and international postal codes
  • Currency (symbols, positions of currency markers)
  • Weights and measures
  • Paper sizes
• Writing Conventions
  • Date/time format, including use of different calendars
  • Time zones (UTC in internationalized environments)
  • Formatting of numbers (decimal points, positioning of separators, character used as separator)
• Any other aspect of the product or service that's subject to regulatory compliance

Cultural values and social context

Practice

The current prevailing practice is for applications to place text in resource strings which are loaded during program execution as needed. These strings, stored in resource files, are relatively easy to translate. Programs are often built to reference resource libraries depending on the selected locale data.
   Thus to get an application to support multiple languages one would design the application to select the relevant language resource file at runtime. Resource files are translated to the required languages. This method tends to be application-specific and at best, vendor-specific. The code required to manage date entry verification and many other locale-sensitive data types also must support differing locale requirements. Modern development systems and operating systems include sophisticated libraries for international support of these types.
   New methods are evolving all the time to handle these complex issues. One such method, known as NLSO or Natural Language Support Objects uses databases to store resource strings. Another approach is the elimination of all references to culture, politics, history, etc.; avoidance of images (especially text embedded in images); and use of a controlled language. NLSO is available open source & also the commercial version from ComChatter.com Ltd, of the United Kingdom

Difficulties

However user requirements might differ significantly over cultures, for example, reading from right to left as in Persian, Hebrew or Arabic may require additional changes to the GUI. OpenOffice.Org solves this with compilation switches.
   Some say that the development team needs someone who understands foreign languages and cultures and has a technical background and such a person may be difficult to find. Others argue that the commercial case to localize products into multiple languages is very obvious, and that all is needed is a budgetary commitment from the producer to finance the considerable costs. It costs more to produce products for international markets, but in an increasingly global economy, English only is scarcely an option. For instance, if a message displayed to the user in one of several languages is modified, all of the translated versions must be changed. Software libraries that aid this task are available, such as gettext.
   Since open source software can generally be freely modified and redistributed, it's more prone to internationalization. Most proprietary software is only available in languages considered to be economically viable whereas the KDE project, for example, has been translated into over 100 languages.

Further Information

Get more info on 'Internationalization And Localization'.

External Link Exchanges Do you know how hard it is to get a link from a large encyclopaedia? Well we're different and will prove it. To get a link from us just add the following HTML to your site on a relevant page: <a href="http://internationalization_and_localization.totallyexplained.com">Internationalization and localization Totally Explained</a> Then simply click through this link from your web page. Our crawlers will verify your link, extract the title of your web page and instantly add a link back to it. If you like you can remove the words Totally Explained and embed the link in article text.    As long as your link remains in place, we'll keep our link to you right here. Please play fair - our crawlers are watching. Your site must be closely related to this one's topic. Any kind of spamming, dubious practises or removing the link will result in your link from us being dropped and, potentially, your whole site being banned.